Required / Supported Hardware
Hardware Requirements
NetBSD will run on an Amiga or DraCo with the following mimimum hardware
configuration.
CPU
NetBSD requires a 68020 or later CPU to run. In
addition you must have a memory management unit (MMU). A Floating Point Unit (FPU) is recommended but not required. 68LC040, 68040V
and 68LC060 based machines don't work correctly at the moment.
Note:Despite what some FAQ's and Installation Guides may say NetBSD includes support for the 68060
Memory
Theoretically NetBSD can run in only 2MB of fast-RAM, however you will not
be able to do anything more than boot! A minimum of 4MB of fast-RAM is
recommended for a useable system, 8MB if you plan to run X-Windows.
NetBSD also requires at least 1MB of chip-RAM which is used during
booting. The kernel is loaded into chip-RAM and then copied into the
largest chunk of fast-RAM available.
Note: The Generic kernel is over 1MB in size and
therefore requires 2MB chip-RAM to load. If you only have 1MB chip-RAM you
will need to use the basic install kernel.
Diskspace
Although it is possible to boot NetBSD from floppy to obtain a useable
system you must have a Hard Disk. The amount of disk space required
depends upon how much of NetBSD you plan to install and what extra
components you intend to install. A small but working system needs 50 to
80MB of disk space. For a more detailed guide to disk space usage see the
installation guide
Supported Hardware
NetBSD has built in support for the following hardware devices.
Unfortunately if a device is not on the list then it is not supported by
NetBSD 1.3 and can't be used. New devices are, however, being added all
the time and you may be able to find an experimental or beta driver in
NetBSD current.
A4000/A1200 IDE controller.
SCSI host adapters:
33c93 based boards: A2091, A3000 builtin and GVP series
II.
53c80 based boards: 12 Gauge, IVS, Wordsync/Bytesync and
Emplant.
53c710 based boards: A4091, Magnum, Warp Engine, Zeus
and DraCo builtin.
FAS216 based SCSI boards: FastLane Z3, Blizzard I and
II, Blizzard IV, Blizzard 2060, CyberSCSI MK I and II.
Video controllers:
ECS, AGA and A2024 built in on various Amigas.
Retina Z2, Retina Z3 and Altais.
Cirrus CL GD 54xx based boards: GVP Spectrum, Picasso II, II+ and IV, Piccolo and
Piccolo SD6.
Tseng ET4000 based boards: Domino and Domino16M proto, oMniBus, Merlin.
A2410.
Cybervision 64.
Cybervision 64/3D.
Audio I/O:
Amiga builtin (currently 8bit-mode only).
Melody Mpeg-audio layer 2 board.
Ethernet controllers:
A2065 Ethernet
Hydra Ethernet
ASDG Ethernet
A4066 Ethernet
Ariadne Ethernet
Quicknet Ethernet
Arcnet controllers:
A2060 Arcnet
Tape drives:
Most SCSI tape drives, including
Archive Viper, Cipher SCSI-2 ST150.
Scanners:
SCSI-2 scanners behaving as SCSI-2 scanner
devices
HP Scanjet IIMustek SCSI scanner
CD-ROM drives:
Most SCSI CD-ROM drives
Serial cards:
MultiFaceCard II and III
HyperCom Z3 and HyperCom 4
A2232
Amiga floppy drives.
Amiga parallel port.
Amiga serial port.
Amiga mouse.
DraCo serial port, including serial mouse.
DraCo parallel printer port.
Real-time clocks: A2000, A3000, A4000 builtin, DraCo builtin
Known problems with some hardware:
The Emplant SCSI adapter has been reported by a party to
hang after doing part of the installation without problems.
CV64/3d is not used, if in a Zorro II machine. Experimental support for this mode is in the kernel
sources, and you can try it by using ''option "CV3DONZORRO2"'' in your kernel configuration file
when compiling your own custom kernel.
SCSI scanner support is machine independant, so it should
work, but hasn't been tested yet on most Amiga configurations.
There are reports that it Mustek and HP Scanjet hang if
accessed from the A3000. This might apply to other
33C93-Adapters, too.
Our floppy driver doesn't notice when mounted floppies are write-protected at the moment. Your
floppy will stay unchanged, but you might not notice that you didn't write anything due to the buffer
cache. Also note that HD floppy drives only get detected as such if a HD floppy is inserted at boot
time.